Date: Fri, 07 Dec 2007 08:44:37 +0100 From: Patrick van Iersel <pviersel@office.caiw.nl> To: Eugene Grosbein <eugen@kuzbass.ru> Cc: freebsd-stable@FreeBSD.org Subject: Re: Extreme load with local password db lookups Message-ID: <C37EB875.397C1%pviersel@office.caiw.nl> In-Reply-To: <4758DCDA.ED9F0C56@kuzbass.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
> From: Eugene Grosbein <eugen@kuzbass.ru> > Organization: SVZServ > Date: Fri, 07 Dec 2007 12:40:42 +0700 > To: Jeremy Chadwick <koitsu@FreeBSD.org> > Cc: Patrick van Iersel <pviersel@office.caiw.nl>, freebsd-stable@FreeBSD.org > Subject: Re: Extreme load with local password db lookups > > Jeremy Chadwick wrote: > >>>> Here's the situation. We have an web/ftp server with around 74000 users >>>> defined in the local unix password database. On 4.9-stable which it is >>>> running now, there is no noticable load when lookups are done (logins via >>>> ftp, ~user lookups from apache etc.). We want to migrate this system to >>>> 6-stable. >>>> However on 6-STABLE (FreeBSD 6.3-PRERELEASE #0: Wed Dec 5 13:35:05 CET >>>> 2007) these same lookups cause very high load and things slow down to a >>>> crawl. >>>> >>>> Does anybody have an idea what causes this behavior? >>>> >>>> Thanx in advance for any insights. >>> >>> Take a look to your /etc/nsswitch.conf. If you do not use NIS, >>> try to change lines for 'group' and 'passwd' to look like this: >>> >>> group: files >>> passwd: files >> >> The default value is "compat" on both RELENG_6 and RELENG_7. I don't >> think switching to "files" will fix his problem (I'll be very surprised >> if it does). > > See http://www.freebsd.org/cgi/query-pr.cgi?pr=75855 > It seems the regression from RELENG_4 is still here. > > There are so many regressions in performance that I still > prefer to invest time to patch bsd.ports.mk to support 4.x > (and have a success, I use fresh ports with 4.x these days) > then upgrade my UP boxes to 6.x and suffer from loss of performaince. For what it's worth, Eugene's suggestion of changing nsswitch.conf actually helps. It was mentioned in the PR above as well. It's still a workaround but it works good enough for me now. Thanx guys. Best regards, Patrick.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C37EB875.397C1%pviersel>